Skip to content

feat: opt-in resolve mode for previous review cleanup (#43) - #51

Merged
brucearctor merged 1 commit into
mainfrom
feat/resolve-discussions-43
Jul 26, 2026
Merged

feat: opt-in resolve mode for previous review cleanup (#43)#51
brucearctor merged 1 commit into
mainfrom
feat/resolve-discussions-43

Conversation

@brucearctor

@brucearctor brucearctor commented Jul 26, 2026

Copy link
Copy Markdown
Contributor

Closes #43

Adds cleanup_mode config to control how previous bot comments are handled:

  • delete (default): Current behavior — deletes old comments
  • resolve: Resolves GitLab discussions instead of deleting (GitHub falls back to delete with a warning)

Config

  • Flag: --cleanup-mode delete|resolve
  • Env: CODE_REVIEWER_CLEANUP_MODE
  • YAML: cleanup_mode: resolve

Changes

  • config/config.go: New CleanupMode type, flag, env, yaml, validation
  • vcs/types.go: Added CleanupMode to SubmitReviewRequest
  • gitlab/client.go: ListDiscussions(), ResolveDiscussion(), ResolvePreviousReviews(), new put() helper
  • github/client.go: Logs warning on resolve mode, falls back to delete
  • reviewer/output.go: Passes config cleanup mode through
  • Config and integration tests added

@coderabbitai

coderabbitai Bot commented Jul 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@brucearctor, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 87286f1c-a253-49fb-aa11-8d2b185499a2

📥 Commits

Reviewing files that changed from the base of the PR and between d897a14 and db37865.

📒 Files selected for processing (5)
  • internal/config/config.go
  • internal/github/client.go
  • internal/gitlab/client.go
  • internal/reviewer/output.go
  • internal/vcs/types.go
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/resolve-discussions-43

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@brucearctor
brucearctor merged commit 984e92d into main Jul 26, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

feat: resolve discussions instead of delete (opt-in cleanup_mode)

1 participant

@brucearctor